Electronic rights management and authorization system

ABSTRACT

An electronic rights management and authorization system to account for the dynamic, multi-dimensional, and granular nature of rights. A database structure divides works and rights into two related tables. A works table includes information sufficient to identify works managed by the system, while a rights table identifies a right associated with a work and includes one or more date fields delimiting the right. The rights table may also include type of use information. Additional tables, such as a work relation table, a party table, or an order table, may be provided. Software is used to manage and to query the database structure. The system has broad applicability to intellectual, real, and personal property; contract management; and similar items. The system may be implemented in standalone mode, through the client/server model of computing, or over the Internet.

RELATED APPLICATIONS

[0001] This is a continuation application of application Ser. No.09/370,953 which was filed on Aug. 10, 1999 by Woodrow W. Johnson,Christine J. Adkins, Jon Yoh and Thomas M. Parece, entitled “ElectronicRights Management and Authorization System” which is a continuation ofapplication Ser. No. 08/625,905, filed Apr. 1, 1996, now U.S. Pat. No.5,991,876.

FIELD OF THE INVENTION

[0002] The present invention relates to an electronic rights managementand authorization system and, in particular, to a system for managingrights and authorizing uses of intellectual property rights, realproperty interests, contract interests, and similar items.

BACKGROUND OF THE INVENTION

[0003] Various organizations participate in the activity of rightsmanagement. Municipalities maintain title offices in which the ownershipof real property is recorded. Federal and state governments maintainoffices for the registration and recording of intellectual propertyrights, including rights in patents, trademarks, copyrights, and maskworks. Collective rights organizations serve as clearinghouses forlicensing various works. Two well-known collective rights organizationsare the American Society of Composers, Authors and Publishers (ASCAP)and Broadcast Music Incorporated (BMI). The assignee of the presentinvention, Copyright Clearance Center, Inc. (CCC), is a third collectiverights organization. Several other similar organizations exist,including stock photography agencies and multimedia licensing groups.

[0004] A variety of schemes for managing rights have been devised. Anearly technique, which continues to be used by many, is the use of indexcards. Each card represents and identifies a unique item or work indexedby the system, such as a tract of land, a patent, or a publication.Information associated with each item or work may be added to the cards.Thus, for a tract of land, one may include the owner; for a patent, theassignee of the patent; and for a publication, its author. Otherinformation is often associated with each card.

[0005] With the advent of computing, most index card systems have beentranslated to electronic form. Electronic systems capture theinformation previously collected on index cards and organize thisinformation into flat-file or relational databases. Flat-file databasesconsist of one file, which contains one record for each unique item orwork. For example, prior art systems organize real property interests insystems that include one record for each tract of land within a county'sboundaries. Other prior art systems for land management include onerecord for each transaction that has occurred within a county'sboundaries.

[0006] Relational databases contain at least two database files. Forexample, literary works are managed in prior art systems that include afirst database file with an entry for each work, linked to a seconddatabase file with author information. To the extent that any authorwrote multiple works, the use of the second database file saves storagespace. However, these and other prior art electronic rights managementsystems do not offer functional advantages over the index card systemother than in the time it takes to perform a search and in the physicalstorage constraints of the system.

[0007] In particular, prior art systems fail to address three concernsthat have become increasingly apparent in the context of digital andmultimedia works. First, rights are dynamic. For example, a periodicalmay be published by a first publisher and later acquired by a secondpublisher. The second publisher may, for example, permit duplication ofmaterials from the last twelve months for a base fee plus $1.25 perpage, while materials from a prior year are at a lower base fee plus 25¢per page. The first publisher may retain rights to materials prior to aparticular date. An effective rights authorization system shouldrecognize the different publishers as well as the time-based ratechanges inherent in the second publisher's pricing. It should alsopermit this information to be altered over time.

[0008] Second, rights are often not one dimensional. Several types ofuse may be permissible for different items or works. Some types of usemay also foreclose others, such as a one-time grant of an exclusiveright. For published works, rights include the traditional copyrightrights, each of which is infinitely divisible. The reproduction rightmay be licensed at different rates for different customers (e.g.,educational, not-for-profit, or commercial user rates), for differentmedia of use (e.g., paper, CD-ROM, intranet, or Internet), for differentvolumes of use (e.g., one copy, several copies, or an unlimited numberof copies), and for different times (e.g., a particular year). Thesetypes of use may further be subject to retained rights (attribution,reversion, “moral” and the like) of the author in certain jurisdictions.An effective rights authorization system should be capable ofrecognizing these types of use and/or restrictions.

[0009] Third, items or works are granular. A journal contains manyarticles, each of which may have different ownership, use, and pricingparameters. A particular article may have subcomponents with differentcharacteristics, such as embedded photographs, illustrations, andcharts. For example, a potential licensee interested only in aphotograph that appears in an article may find that rights to thephotograph are retained by the photographer and are not available, orthat rights to the photograph are available independent of, and ondifferent terms than, rights to the entire article. A granter of rightsmay also combine various items or works into different packages. Apublisher may price rights to a collection of ten journals at a reducedrate. A potential licensee interested in the two most-popular journalsmay find this pricing option attractive, while a potential licenseeinterested in two lesser-known journals (already priced at lowindividual rates) may find this option unattractive. In either case, aneffective rights authorization system should be flexible and allowgranularities.

[0010] These concerns are not limited to new media works. Similarproblems arise, for example, in the context of managing real property.The problem of time variability is reflected in the illustrativesituation where the owner of a parcel of land offers the parcel forlease, with the subsequent lessee then offering the land for sublet at afirst rate for commercial use and at a second rate for non-profit use,both rates escalating over time. Type of use and granularity may also beinvolved. The owner of adjoining beach-front properties may offer aneasement to the set. This involves a type of use other than ownership,with a granularity of more than one parcel of land. An effective rightsmanagement and authorization system should recognize these complexarrangements.

SUMMARY OF THE INVENTION

[0011] The present invention provides an electronic system for managingand authorizing rights. With the present invention, clearinghousefunctions may be provided, while accounting for the problems of timevariability, type of use, and granularity. The present inventionprovides for fully automated rights management and authorization.

[0012] The data structure of the present invention divides works andrights. A first data file contains works. Each record in the works tableincludes information sufficient to identify one or more works managed bythe system. A second data file contains rights. Each record in therights table is associated with one or more works and may include up tothree date fields, including a validity date field, an effective datefield, and a permission date field. The function of these date fields isexplained in the detailed description of the invention. In general, atleast one date field is needed to account for the dynamic nature ofrights.

[0013] To account for different types of use, the rights table mayinclude a type of use field. This field identifies a particular rightfor which authorization is given (or withheld). For example, in a systemfor copyright clearance, the type of use may be the right to reproducein the context of a university coursepack. A right to reproduce forcommercial purposes may be withheld. This field may further includeprice information for the type of use, have a separate field for suchinformation, or be linked to a separate table that provides suchinformation.

[0014] To account for granularity, a work relation table may be added toshow relationships between works. In a system for copyright clearance,this table could show, for example, that a photograph is embedded in anarticle, that a particular short story is printed in three differentanthologies, or that a publisher offers a license to a collection ofjournals organized as a workset. The fields in this table and itsfunctionality are explained in the detailed description of theinvention.

[0015] Many other enhancements may be added. One such enhancement is theinclusion of a party table to provide detailed data about parties in thesystem. While parties will generally include all rights holders, partiesmay include any other individual, group, or organization with arelationship to the rights and authorizations managed by the system.This information may be used for client management, billing and payment,and aggregation functions. A second enhancement is the inclusion of anorder table to provide a dynamic log of right authorizations anddenials. Those of ordinary skill in the art will conceive of otherenhancements to the system herein described.

[0016] A rights management and authorization systems according to thepresent invention combines this data structure with one or more softwareprograms or tools for controlling and querying the data structure.Software is provided on the management side for performing work andright maintenance, such as adding, deleting, and editing entries.Software is also provided on the authorization side for querying thedatabase to determine, for example, whether or not to authorize aparticular use posed by a potential licensee.

[0017] A system according to the present invention may permitrightsholders themselves to add, delete, and edit rights through directaccess to the rights management side of the system. A system accordingto the present invention may additionally or alternatively permitpotential licensees to obtain (or be denied) authorizations throughdirect access to the rights authorization side of the system. Thus,unlike prior art systems, the present invention enables automated rightsmanagement and authorization. This system may be provided over aproprietary network, the Internet, or other suitable means.

BRIEF DESCRIPTION OF THE DRAWINGS

[0018] The above and further advantages of the invention may be betterunderstood by referring to the following description in conjunction withthe accompanying drawings in which:

[0019]FIG. 1 shows an illustrative computer system to which the presentinvention applies;

[0020]FIG. 2 shows a block diagram of the components of a computersystem to which the present invention applies;

[0021]FIG. 3 shows a diagram of a first embodiment of a data structurecontemplated by the present invention;

[0022]FIG. 4 shows a diagram of a second embodiment of a data structurecontemplated by the present invention;

[0023]FIG. 5 shows an illustrative user interface for performing workmanagement functions;

[0024]FIG. 6 shows an illustrative user interface for performing rightmanagement functions; and

[0025]FIG. 7 shows an illustrative user interface for performing anauthorization inquiry.

DETAILED DESCRIPTION 1. Computer System

[0026]FIG. 1 shows an illustrative computer system 100 to which thepresent invention applies. Computer system 100 contains data storagedevices, a central processing unit, a power source, and connections forexternal devices. External devices typically connected to computersystem 100 include one or more output devices, such as video monitor102, and one or more input devices, such as keyboard 104 and pointingdevice 106. Computer system 100 may be any of several commerciallyavailable computer systems available from Apple, Compaq, Digital,Hewlett Packard, IBM and others. A successful prototype of the systemhas been developed using Digital Equipment Corporation's Alpha 2100system, but initial commercial implementation of the system isanticipated to be on DEC's Alpha 8200 system. Those of ordinary skill inthe art may select and implement the present invention on other computersystems.

[0027]FIG. 2 shows a block diagram of the components of a computersystem to which the present invention applies. Central processing unit200 contains one or more microprocessors for executing the computersoftware programs necessary to implement the present invention. Centralprocessing unit 200 is typically connected to primary storage 202 andsystem bus 204. Primary storage 202 is typically volatile storage, suchas RAM. The programs and data for implementing the present invention arestored on a temporary basis in primary storage 202 during execution.Typically, only a portion of the programs and data fit in primarystorage 202 at any particular time. Cache memory may also be includedwith central processing unit 200 or primary storage 202 to speed programexecution.

[0028] System bus 204 connects the components of the computer system,and may be based on an open architecture, such as Peripheral ComponentInterconnect (PCI), or on a proprietary design. Several devices areconnected to system bus 206. Secondary storage 206 is typicallynonvolatile storage, such as an optical or magnetic disk drive. Theprograms and data for implementing the present invention are stored on apermanent basis in secondary storage 206. Input device 208 may includekeyboard 104 or pointing device 106, and output device 210 may includevideo monitor 102. In some computer systems, input device 208 and outputdevice 210 are connected directly to central processing unit 200, ratherthan through system bus 204.

[0029] While the computer system may be limited to the previouselements, the addition of network interface 212 and client 214 addsflexibility to the system and enables operation under the client/servermodel of computing. Network interface 212 may be a local-area orwide-area network card, a modem, a gateway to the Internet or anInternet service provider, or a similar interface. Client 214 may be acomputer system similar to the one used to implement the presentinvention, or more typically, a low-cost personal computer of the typeused in homes or offices.

2. First Illustrative Data Structure

[0030]FIG. 3 shows a diagram of a first embodiment of a data structurecontemplated by the present invention. This data structure may be used,for example, in a system for clearing rights to photographs. In thisembodiment, it is assumed that all of the works are photographs and thatthe only right available for authorization is the right to duplicate. Itis further assumed that some rights are held by photographers, whilesome rights are held by others. This embodiment of the invention couldbe used over a network service to offer and obtain rights tophotographic images.

[0031] Works table 300 contains information about the works managed inthe system. Here, these works are photographs. Information about eachphotograph is contained in one record in works table 300, where eachrecord includes work_instance field 302, work_title field 304, andwork_author field 306. Work_instance field 302 contains an identifierfor a photograph. This identifier may be software generated or based ona standard classification scheme like the ISBN numbering scheme forwritten works. The identifier is generally numeric, but may also besymbolic or alphanumeric. Each identifier should be unique, so as todistinguish similarly titled and authored works. Work_title field 304 isan alphanumeric field that contains the title of the photograph.Work_author field 306 contains a reference or link to a party_instancefield 320 of party table 318. This link identifies the work'sphotographer. In alternative embodiments, work_author field 306 maycontain the name of the author if complete party information does notneed to be maintained. This may arise, for example, with regard to worksnow in the public domain. For efficiency, works table 300 may be indexedor keyed on work_instance field 302 and other fields. In addition, workstable 300 may include other fields, such as a field containing a bit-mapor similarly-coded image of the photograph that may be viewed through anon-line service. Table 1 shows an illustrative works table containingtwo photographs titled, “Early Sunrise,” and two other photographs.TABLE 1 Work_Instance Work_Title Work_Author W_1 Early Sunrise P_1 W_2Fall Foliage P_3 W_3 Spring Flowers P_1 W_4 Early Sunrise P_2

[0032] Rights table 308 contains information about the rights managed inthe system. In this example, the only managed right is a duplicationright, so this type of use is assumed (rather than specified in aseparate field). Information about each right is contained in one recordin rights table 308, where each record includes right_instance field.310, right_holder field 312, related_work field 314, and validity_datefield 316. Right_instance field 310 contains an identifier for a right.This identifier will generally be assigned by the software and willgenerally be numeric. It is possible, though, to have other assignmentprotocols and to have symbolic or alphanumeric identifiers. Eachidentifier should be unique, so as to distinguish each right.Right_holder field 312 contains a reference or link to a party_instancefield 320 in party table 318. This link identifies the right holder.Here, the right holder may be a photographer or some other party.Related_work field 314 contains a reference or link to a work_instancefield 302 in works table 300. This link identifies the work to which theright pertains. Validity_date field 316 is a date field (or fields)setting forth the time period in which authorization is given to grantthe right. For efficiency, rights table 308 may be indexed or keyed onright_instance field 310 and other fields. In addition, rights table 300may include other fields, including those discussed in the secondembodiment of this invention. Table 2 shows an illustrative rights tablefor the works shown in Table 1. TABLE 2 Right_Instance Right_HolderRelated_Work Validity_Date R_1 P_1 W_1 1996-98 R_2 P_3 W_2 1996-99 R_3P_1 W_3 1996-98 R_4 P_2 W_4 1996-99 R_5 P_4 W_1 1996-97 R_6 P_4 W_41996-97

[0033] In Table 2, six rights are available. These rights includeduplication rights from the photographers for the four works managed inthe system. These rights are recorded in the records identified as R_1through R_4. Two other rights are available. Record R_5 is for the firstphotograph titled, “Early Sunrise,” and record R_6 is associated withthe other photograph with this same name. Rights to both of thesephotographs are available from another right holder, identified as P_4.As shown later in Table 3, this right holder is Jones' Gallery, whichacquired authorization rights to these photographs for 1996-97 inconnection with an exhibition of “Early Sunrise” photographs.

[0034] Party table 318 contains information about the parties associatedwith the system. In alternative embodiments, the information in partytable 318 may be stored directly in works table 300 and rights table308. A separate table is used to conserve storage space where multiplerecords are associated with the same party. Information about each partyis contained in one record in party table 318, where each recordincludes party_instance field 320, party_name 322, and party_address324. Party_instance field 320 contains an identifier for a party. Thisidentifier will generally be assigned by the software and will generallybe numeric. It is possible, though, to have other assignment protocolsand to have symbolic or alphanumeric identifiers. Each identifier shouldbe unique, so as to distinguish each party. Party_name field 322 is analphanumeric field that contains the party's name. Party_address field324 is an alphanumeric field that contains the party's address. Partytable 318 may include other fields pertinent to the parties. Forefficiency, party table 318 may be indexed or keyed on party_instancefield 320 and other fields. Table 3 shows an illustrative party tablefor the parties associated with Tables 1 and 2. TABLE 3 Party_InstanceParty_Name Party_Address P_1 Lopez, David Winter Street Anytown, USA10000 P_2 Connor, Julie Spring Street Anytown, USA 10000 P_3 Gregory,Eileen Fall Drive Anytown, USA 10000 P_4 Jones' Gallery Commerce ParkAnytown, USA 10001

3. Second Illustrative Data Structure

[0035]FIG. 4 shows a diagram of a second embodiment of a data structurecontemplated by the present invention. This data structure may be usedin a system for clearing rights to any type of work. These works mayinclude anything subject to copyright or any similar right. Anon-exclusive list of works includes written works, such as books,periodicals and their component parts; visual works, such as photographsand sculpture; audio works, such as music; audiovisual works, such asmovies; and computer works, such as software programs and databasecompilations. This data structure may also be adapted for use with othertypes of interests, such as those in patents, trademarks, trade secrets,mask works, real property, personal property, contracts, or any otheritem that may be subject to conveyance, license, sale, or similartransaction.

[0036] The second embodiment of the data structure includes elementsfrom the first embodiment of the data structure. Works table 400 and itswork_instance field 402, work_title field 404 and work_author field 406are similar in content and function to works table 300 and its threeconstituent fields. Works table 400, though, will typically include alarger variety of works. Party_table 428 and its party_instance field430, party_name field 432 and party_address field 434 are similar incontent and function to party table 318 and its constituent fields.Party table 400, though, will typically include a more diverse set ofparties.

[0037] The second embodiment of the data structure includes severalelements not found in the first embodiment of the data structure. Whilerights table 408 and its right_instance field 410, right_holder field412, related_work field 414, and validity_date field 422 have similarcontent and serve a similar function as rights table 308 and itssimilarly-named fields, there are several new fields in rights table408.

[0038] Type_of_use field 416 sets forth the type of use associated withthe right. This field may be numeric or alphanumeric, linked to aseparate table, or defined in some other way. This field captures, forexample, the fact that a right concerns different customers (e.g.,educational, not-for-profit, or commercial users), different media ofuse (e.g., paper, CD-ROM, intranet, or Internet), and different volumesof use (e.g., one copy, several copies, or an unlimited number ofcopies). Right_fee field 418 sets forth the fee associated with theright and type of use. This field may be a numeric field, contain aformula, or be defined in some other way. Right_grant field 420 is aboolean field that records whether or not a right may be granted. Thisfield is used in response to inquiries for rights previously denied, toindicate that a denial is firm and not merely a new inquiry. This fieldis also used for archival purposes, to substantiate switches over timebetween authorization and denial for essentially identical rights.

[0039] In the second embodiment of the invention, two date fields inaddition to validity_date field 422 are included in rights table 408.Effective_date field 424 is a date field (or fields) setting forth thetime period for which a right is effective. The effective date maydiffer from the validity date. For example, a right may be effective asto material published in a periodical from 1985 through 1990, althoughthis right is only valid to grant during 1995. A third date field,permission_date field 426, is a date field (or fields) setting forth thetime period in which a potential licensee may exercise a right. In theabove example, the rights holder may permit a license to be grantedduring 1995 for the 1985-90 material, which license may be exercisedduring the three year period from 1995 through 1997. The validity dateis 1995; the effective date is 1985-90; and the permission date is1995-97.

[0040] Table 4 shows a portion of a rights table for an illustrativeauthorization scheme. A right holder (record P_5 in party table 430) hasa two year contract, entered Jan. 1, 1996, with an organizer of a rightsmanagement and authorization system. Under the contract, the organizermay grant three year licenses to make paper photocopies (designated as“R”) of right holder's magazine (record W_9 in works table 400). Duringthe first year of the contract, rights are offered at a base fee(designated as “B”) of $1.00 plus a per page copy fee (designated as“P”) of 5¢ per page. During the second year of the contract, rights areoffered at a base fee of $1.10 plus 6¢ per page. If rights are obtainedduring the first year, the price is locked in at the first-year rate.Commercial entities (designated as “Com”) are charged twice the fee ofeducational entities (designated as “Ed”). TABLE 4 Right_InstanceRight_Holder Related_Work Type_of_Use Right_Fee Right_GrantValidity_Date Effective_Date Permission_Date R_10 P_5 W_9 REd B1000P005Yes 1996 All 1996-98 R_11 P_5 W_9 REd B110P006 Yes 1997 All 1997-99 R_12P_5 W_9 RCom B200P010 Yes 1996 All 1996-98 R_13 _(——)5 W_9 RCom B220P012Yes 1997 All 1997-99

[0041] The second embodiment of the data structure adds work relationtable 436. Work relation table 436 accounts for granularity, where eachrecord in the table includes parent_work_instance 438 andchild_work_instance 440. Each of these fields contains a reference orlink to a works_instance field 402 in works table 400. For efficiency,work relation table 436 may be indexed or keyed on either or bothfields. In alternative embodiments, the data contained in work relationtable 436 may be included directly in works_table 400.

[0042] Table 5 shows a works table, Table 6 shows a work relation table,and Table 7 shows an abridged rights table, which collectivelyillustrate the concept of granularity. The work titled, “The GoldenParakeet,” is a children's story that is published on its own andcontained in an anthology titled, “The Best Bedtime Stories of 1994.”The story also includes an illustration titled, “The Winding River,” byan artist other than the author of the story. The works table includes asecond anthology of stories titled, “The Best Bedtime Stories of 1995.”The publisher of the two anthologies offers a blanket license to theworks, designated as “Bedtime Stories Work Set.” As shown in Table 7,the only right available to the works in Table 5 is a right to reprint“The Bedtime Stories Work Set” on a per page fee. TABLE 5 Work_InstanceWork_Title Work_Author W_20 The Golden Parakeet P_10 W_21 The WindingRiver P_11 W_22 The Best Bedtime Stories of 1994 P_12 W_23 The BestBedtime Stories of 1995 P_12 W_24 Bedtime Stories Work Set P_12

[0043] TABLE 6 Parent_Work_Instance Child_Work_Instance W_20 W_21 W_22W_20 W_24 W_22 W_24 W_23

[0044] TABLE 7 Right_Instance Right_Holder Related_Work R_30 P_12 W_24

[0045] If a potential licensee seeks a right to reprint theillustration, “The Winding River,” the following steps may be executedin authorization software. The work “The Winding River” is identified asrecord W_21 in Table 5. A search of the related_work field in Table 7for W_21 finds no available rights. The software then moves up onelevel, to determine whether W_21 is contained in another work to whichrights are available. A search of the child_work_instance field in Table6 for W_21 finds that it is contained in W_20, the short story. A secondsearch in Table 7 for W_20 again finds no available rights. Moving upanother level, a search of Table 6 for W_20 finds that it is containedin W_22, the first anthology. A third search in Table 7 for W_22 againfinds no available rights. Moving up another level, a search of Table 6for W_22 finds that it is contained in W_24, the work set. A fourthsearch of Table 7 for W_24 finds that R_30 provide the necessary rights.Of course, depending on the rights inquiry, the search process may workin the opposite direction or through alternative but equivalent steps.

[0046] The second embodiment of the data structure includes order table442. This table provides a dynamic log of right authorizations anddenials, where each record includes several fields. Order_instance field444 contains an identifier for an order. This identifier may be softwaregenerated or linked to a paper reference like a purchase order number.While the identifier may be numeric, symbolic, or alphanumeric, eachidentifier should be unique. Order by field 446 contains a reference orlink to a party_instance field 430 of party table 428. This linkidentifies the party placing the order. Order_date field 448 is a datefield for recording the date of the order. Order_right field 448contains a reference or link to a right_instance field 410 of rightstable 408. This link identifies the right ordered. Order_status field452 may be used to track the status of an order. For efficiency, ordertable 442 may be indexed or keyed on order_instance field 444 and otherfields. Typically, order table 442 will include other fields andstructures to accommodate more complex transactions, such as multiplerights under a single purchase order.

4. Computer Software Programs

[0047] The data structure from above is combined with one or moresoftware programs or tools for controlling and querying the datastructure. Software is provided on the management side for performingwork and right maintenance, such as adding, deleting, and editingentries. Software is also provided on the authorization side forquerying the database to determine, for example, whether or not toauthorize a particular use posed by a potential licensee. The computersoftware programs for controlling and querying the data structure may ormay not be on the same physical data storage space as the datastructure, and often will not be.

[0048] On the server side of the system for rights management, favorableresults have been achieved with a prototype system based on OracleVersion 7.1.3 database software running under Open VMS on a DEC Alpha2100. An initial commercial system is contemplated in which Oracle 7.2is used on a DEC Alpha 8200. On the client side of the system for rightsauthorization, favorable results have been achieved using personalcomputers with Intel microprocessors and Microsoft operating systemsrunning object-oriented applications built under PowerBuilder Version4.0. Those of ordinary skill in the art may select and implement thepresent invention on other computer systems, and could quickly andeasily construct a single-user model from a database system such asAccess, dBase, FoxPro, or Quattro. It is contemplated that clients mayconnect to the server side of the system through Internet connections orsome other type of on-line link, and communicate with the systemthrough, for example, TCP/IP and/or DCE protocols, or their equivalent.

[0049]FIG. 5 shows an illustrative user interface 500 on the managementside for performing work maintenance functions. User interface 500includes a view of a constructive index card 502 on which informationstored or associated with a record in the works table is recorded. Here,card 502 includes title field 504, author name field 506, and authoraddress field 508. These fields store or control the data suggested bytheir names. Card 502 further includes continue button 510 for alertingthe system that operations on a card have been completed. Typically,interface 500 would include drop down menus for, among other things,entering modes to find, add, delete, and edit records.

[0050]FIG. 6 shows an illustrative user interface 600 on the managementside for performing right management functions. User interface 600includes a view of a constructive index card 602 on which informationstored or associated with a record in the rights table is recorded.Here, card 602 includes related work field 604, right holder field 606,type of use field 608, grant field 610, fee formula field 612, validitydate field 614, effective date field 616, and permission date field 618.These fields store or control the data suggested by their names. Card602 further includes continue button 610 for alerting the system thatoperations on a card have been completed. Typically, interface 600 wouldinclude drop down menus for, among other things, entering modes to find,add, delete, and edit records.

[0051]FIG. 7 shows an illustrative user interface 700 on theauthorization side for performing authorization inquiries. Userinterface 700 includes a view of a constructive index card 702 tospecify a particular right for which authorization is sought. Here, apotential licensee must identify himself, herself, or itself in customerfield 704, specify a particular work for which authorization is soughtin title field 706 and author field 708, and specify a type and volumeof use, respectively, in type of use field 710 and number of copiesfield 712. After this information has been provided, a search may beperformed upon activation of continue button 714. This search woulddetermine whether or not authorization may be given, which informationtypically would be reported to the potential licensee along with priceinformation and an order option. An illustrative search sequence isprovided with the example given with Tables 5, 6, and 7, but those ofordinary skill in the art will devise other search sequences. A moresophisticated interface on the authorization side may change dynamicallyto require more or less information based on a potential licensee'sinput.

5. Other Embodiments

[0052] Although the invention has been shown and described in terms oftwo illustrative data structures and three user interfaces, those ofordinary skill in the art will realize that other data structures andinterfaces may be constructed within the meaning of the presentinvention. Alternative data structures may be designed around rightssimilar to those considered in the two illustrative data structures, orfor different rights. For example, in a patent, trademark, trade secret,or mask work licensing system, the equivalent of a works table may beused to record patents, trademarks, trade secrets, mask works, andrelated sets, while a rights table may store license, assignment, fieldof use, geographical scope, and similar rights and limitations for theseitems. In a real property management and authorization system, theequivalent of a works table may be used to record parcels of land, whilea rights table may store interests in these parcels, such as leaseholds,mineral rights, riparian rights, air rights, easements, and other realproperty rights. In a general system for contract management andauthorization, the equivalent of a works table may be used to recordeach contract or related set of contracts, while a rights table maystore individual interests, rights, licenses, and sublicenses under thecontracts. Those of ordinary skill in the art will also apply theteachings of the present invention to different data types, includingdatabase files, linked lists, multi-dimensional arrays, and other formsof data organization. Based on the software and system used, thespecific rights management and authorization problem addressed, anddesign choices made by the programmer, alternative user interfaces willalso be used. The key feature of the present invention is that a firstdata structure records the item or work, while a separate data structurerecords rights that are available in or to the items and works. Withinthis constraint, several embodiments of the invention may be constructedwithout departing from the spirit of the invention as claimed below.

What is claimed is:
 1. Apparatus for managing and authorizing rightsassociated with compound works that have other works with associatedrights contained therein, the apparatus comprising: a work relationtable that has a record that relates each work that is contained inanother work with that other work; means responsive to a request forrights authorization to a desired work for searching the work relationtable to determine whether the desired work is contained in anotherwork; and means responsive to a determination that the desired work iscontained in another work for determining whether rights are availablefor the desired work.
 2. The apparatus of claim 1 wherein the means fordetermining whether rights are available for the desired work comprisesmeans operable when rights are not available for the desired work fordetermining whether means are available for a work that contains thedesired work.
 3. The apparatus of claim 1 wherein the means forsearching the work table comprises means for searching the work relationtable starting with a work to determine whether the desired work iscontained within that work.
 4. The apparatus of claim 1 furthercomprising a works table that has a record for each work.
 5. Theapparatus of claim 4 wherein the works table includes information takenfrom the work content.
 6. The apparatus of claim 5 wherein theinformation taken from the work content includes the title of the work.7. The apparatus of claim 5 wherein a work is a photograph and theinformation taken from the work content includes a coded image of thephotograph.
 8. The apparatus of claim 1 further comprising an ordertable containing a record for each right authorization and denial. 9.The apparatus of claim 8 wherein the order table contains informationidentifying a party that placed an order.
 10. The apparatus of claim 8wherein the order table contains the status of an order.
 11. Theapparatus of claim 1 wherein the means responsive to a request forrights authorization for searching the work relation table comprisesmeans for determining whether the other work is contained in a thirdwork and, if so determining whether rights are available for that thirdwork.
 12. The apparatus of claim 1 wherein the means responsive to arequest for rights authorization for searching the work relation tablecomprises means for recursively searching the work relation table untila work is found for which rights are available.
 13. The apparatus ofclaim 12 wherein the means for recursively searching the work relationtable generates a right denial if no work is found for which rights areavailable.
 14. The apparatus of claim 1 further comprising a rightstable that has a record for each right and information relating thatright to a work and a right holder.
 15. The apparatus of claim 14wherein the means responsive to a request for rights authorization forsearching the work relation table comprises means responsive to therequest for rights authorization for a work for searching the rightstable to determine if a right is available for the work before the workrelation table is searched.
 16. Apparatus for managing and authorizingrights associated with compound works that have other works withassociated rights contained therein, the apparatus comprising: a workrelation table that has a record that relates each work that iscontained in another work with that other work; means responsive to arequest for rights authorization to a desired work for searching thework relation table to determine whether the desired work is containedin another work; means responsive to a determination that the desiredwork is contained in another work for recursively searching the workrelation table; and means for granting a right authorization if a workis found for which rights are available and a right denial if no work isfound for which rights are available.
 17. The apparatus of claim 16further comprising an order table containing a record for each rightauthorization and denial.
 18. The apparatus of claim 17 wherein theorder table contains information identifying a party that placed anorder.
 19. The apparatus of claim 17 wherein the order table containsinformation identifying the right that was ordered.
 20. The apparatus ofclaim 17 wherein the order table contains the status of an order. 21.The apparatus of claim 16 further comprising a party table identifyingrights holders, individuals, groups and organizations that have arelationship to rights managed by the system.
 22. A method for managingand authorizing rights associated with compound works that have otherworks with associated rights contained therein, the method comprising:(a) providing a work relation table that has a record that relates eachwork that is contained in another work with that other work; (b) inresponse to a request for rights authorization to a desired work,searching the work relation table to determine whether the desired workis contained in another work; and (c) in response to a determinationthat the desired work is contained in another work, determining whetherrights are available for the desired work.
 23. The method of claim 22wherein step (c) comprises determining whether means are available for awork that contains the desired work when rights are not available forthe desired work.
 24. The method of claim 22 wherein step (b) comprisessearching the work relation table starting with a work to determinewhether the desired work is contained within that work.
 25. The methodof claim 22 further comprising: (d) providing a works table that has arecord for each work.
 26. The method of claim 25 wherein step (d)comprises including information taken from the work content in the workstable.
 27. The method of claim 26 wherein the information taken from thework content includes the title of the work.
 28. The method of claim 26wherein a work is a photograph and the information taken from the workcontent includes a coded image of the photograph.
 29. The method ofclaim 22 further comprising: (d) providing an order table containing arecord for each right authorization and denial.
 30. The method of claim29 wherein the order table contains information identifying a party thatplaced an order.
 31. The method of claim 29 wherein the order tablecontains the status of an order.
 32. The method of claim 22 wherein step(b) comprises determining whether the other work is contained in a thirdwork and, if so determining whether rights are available for that thirdwork.
 33. The method of claim 22 wherein step (b) comprises: (b1)recursively searching the work relation table until a work is found forwhich rights are available.
 34. The method of claim 33 wherein step (b1)comprises generating a right denial if no work is found for which rightsare available.
 35. The method of claim 22 further comprising: (d)providing a rights table that has a record for each right andinformation relating that right to a work and a right holder.
 36. Themethod of claim 35 wherein step (b) comprises searching the rights tableto determine if a right is available for the work before the workrelation table is searched.
 37. A method for managing and authorizingrights associated with compound works that have other works withassociated rights contained therein, the method comprising: (a)providing a work relation table that has a record that relates each workthat is contained in another work with that other work; (b) in responseto a request for rights authorization to a desired work, searching thework relation table to determine whether the desired work is containedin another work; (c) in response to a determination that the desiredwork is contained in anther work, recursively searching the workrelation table; (d) granting a right authorization if a work is foundfor which rights are available; and (e) granting a right denial if nowork is found for which rights are available.
 38. The method of claim 37further comprising: (f) providing an order table containing a record foreach right authorization and denial.
 39. The method of claim 38 whereinthe order table contains information identifying a party that placed theorder.
 40. The method of claim 38 wherein the order table containsinformation identifying the right that was ordered.
 41. The method ofclaim 38 wherein the order table contains the status of an 2 order. 42.The method of claim 37 further comprising: (f) providing a party tableidentifying rights holders, individuals, groups and organizations thathave a relationship to rights managed by the system.
 43. A computerprogram product for managing and authorizing rights associated withcompound works that have other works with associated rights containedtherein, the computer program product comprising a computer usablemedium having computer readable program code thereon, including: programcode for creating a work relation table that has a record that relateseach work that is contained in another work with that other work;program code operable in response to a request for rights authorizationto a desired work for searching the work relation table to determinewhether the desired work is contained in another work; and program codeoperable in response to a determination that the desired work iscontained in another work for determining whether rights are availablefor that other work.
 44. A computer program product for managing andauthorizing rights associated with compound works that have other workswith associated rights contained therein, the computer program productcomprising a computer usable medium having computer readable programcode thereon, including: program code for creating a work relation tablethat has a record that relates each work that is contained in anotherwork with that other work; program code responsive to a request forrights authorization to a desired work for searching the work relationtable to determine whether the desired work is contained in anotherwork; program code responsive to a determination that the desired workis contained in another work for recursively searching the work relationtable; and program code for granting a right authorization if a work isfound for which rights are available and a right denial if no work isfound for which rights are available.